Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1426

reference
418-tree-1
name
1426
tree-preservation-order

undefined

418-tpo-1
uprn
address-text
point
POINT (-1.006978 50.891036)
geometry
MULTIPOLYGON (((-1.006907 50.891028,-1.006910 50.891042,-1.006920 50.891055,-1.006936 50.891065,-1.006955 50.891071,-1.006977 50.891074,-1.006999 50.891072,-1.007019 50.891066,-1.007035 50.891056,-1.007045 50.891043,-1.007049 50.891029,-1.007046 50.891016,-1.007036 50.891003,-1.007021 50.890993,-1.007001 50.890986,-1.006979 50.890984,-1.006957 50.890986,-1.006937 50.890992,-1.006921 50.891002,-1.006911 50.891014,-1.006907 50.891028)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL